Update listing's courtscheduler client to the Phase-1 reshaped API:
- search-by-id: GET /courtschedule/search.court-schedules-by-id -> GET
  /sessions; query param courtScheduleIds -> ids
- release slots: DELETE /hearingslots/{id} -> DELETE /sessions/{id};
  action remove.hearing.slots -> release.sessions
- list hearings: PUT /list/hearingslots -> POST /hearings; action
  list.hearings-in-court-sessions -> list.hearings-in-sessions
- extend multiday: POST /extendmultidayhearing/hearingslots -> PATCH
  /hearings/{hearingId} (new HttpPatch helper)
- search-and-book (mags/crown/crown-fallback): GET query endpoints ->
  POST /hearings/{hearingId} with typed JSON body, actions
  mags.search.and.book / crown.search.and.book

Response parsing: mags searchAndBook now reads sessions[0] (was a
hearingSlots object); multiday reads sessions[] (was courtSchedules[]).
Crown-fallback parser unchanged - matched by the courtscheduler
single-day flat-field change. Other responses serialise identical
domain objects, so their parsing is unchanged.

Two request-body shape bugs surfaced against the real courtscheduler on
ns-ste-ccm-22 (both masked by loosely-matching WireMock IT stubs):

1. list.hearings-in-sessions sent hearingSlots[].ids instead of
   courtScheduleIds - the COURT_SCHEDULE_IDS constant was repurposed to
   "ids" for the GET /sessions query param but also built the list body
   key. Split into COURT_SCHEDULE_IDS ("courtScheduleIds", body key) and
   IDS_PARAM ("ids", query param).
2. multiDaySearchAndBook omitted courtCentreId + hearingDate, which
   crown.search.and.book requires (additionalProperties:false). Supply
   them from the hearing context at both call sites; the engine ignores
   them for the anchored path but schema validation requires them present.

Harden CourtSchedulerServiceStub to match on the required nested keys
(courtScheduleId for list; courtCentreId + hearingDate for multiday crown)
so a missing-required-key regression fails the ITs instead of silently
passing. Add unit tests for both body shapes.

…ale draft id on update

mergeCourtScheduleIdsFromNonDefaultDays previously skipped hearingDays that
already carried a courtScheduleId, so on a reschedule the old draft id was
left in place. The downstream fetch then returned the draft session,
isDraft=true propagated to the aggregate, canAllocateForCrown() was closed,
and hearing-rescheduled was emitted with allocated:false.

Fix: remove the early-return guard and allow the nonDefaultDays id to
overwrite the stale draft id when they differ. The new (non-draft) id is then
fetched, isDraft=false is propagated, canAllocateForCrown() opens, and
hearing-allocated-for-listing-v2 + hearing-rescheduled(allocated:true) are
both emitted correctly.

CROWN-only path (mergeCourtScheduleIdsFromNonDefaultDays is only called from
enrichCrownUpdateHearing); MAGS behaviour unchanged.

…day window

The J05 fix commit (205 new lines) shrank SonarQube's NUMBER_OF_DAYS=1 new-code
denominator, flipping new_maintainability_rating to D by surfacing pre-existing
smells inside the new-code period. Clear all 20 counted smells; every change is
behaviour-preserving:

CourtScheduleEnrichmentService (production):
- S3358: extract nested ternaries into locals (startTime fallback, anchor centre
  id, anchor hearing date, isDraft resolution via if/else)
- S6201: use instanceof pattern variables for JsonObject casts
- S1125: simplify the CROWN isPolice boolean expression

Tests (CourtScheduleEnrichmentServiceTest, ListingCommandApiTest, HearingAggregateTest):
- S5786: drop redundant public on JUnit5 test methods
- S6204: Stream.toList() instead of collect(Collectors.toList())
- S1117: rename locals that shadowed fields
- S1128: remove unused import

Unit tests green: CourtScheduleEnrichmentServiceTest 140, ListingCommandApiTest 33,
HearingAggregateTest 173, 0 failures.

… (J05)

Adds CrownUpdateHearingSingleDayIT: a CROWN, originally-unallocated single-day
hearing updated via update-hearing-for-listing with a non-draft courtScheduleId
on nonDefaultDays must end ALLOCATED (polls listing.search.hearing for
$.allocated==true and the new $.startDate).

Locks the end-to-end single-day CROWN allocation outcome (the J05 scenario) at
the integration layer. The update-hearing-for-listing schema is
additionalProperties:false and does not expose hearingDays, so the exact
stale-draft-id merge collision remains covered by the unit/aggregate tests
(CourtScheduleEnrichmentServiceTest, HearingAggregateTest); this IT locks the
e2e outcome. Stubs: stubSearchCourtSchedulesByIdSession(isDraft=false) +
stubListHearingInCourtSessionsForCourtSchedule; dates via ItClock.plusWorkingDays.

Passes in the full listing IT suite (Tests run: 1, 0 failures).

…troom from resolved final schedule

update-hearing-for-listing with only a courtScheduleId on nonDefaultDays (no room
fields) booked the session but never allocated: the handler resolved a null
command-level courtroom, called removeCourtRoom, and canAllocateForCrown() stayed
closed. Allocation only worked when the caller (UI) also supplied the room.

Fix: inverse of stripRoomInfoIfAnyDraft (ADR-005) — when the command carries no
courtroom and every enriched hearingDay resolved to a FINAL (isDraft=false)
session in one distinct room, promote that room to the command level (and backfill
a roomless selectedCourtCentre, which the handler prefers for CROWN). Draft
sessions are roomless on every courtscheduler query path so they can never
qualify; payload-supplied rooms are never overridden; multi-day spans across
different rooms stay underived.

Locked failing-first at both levels: CourtScheduleEnrichmentServiceTest (3 new
derivation tests red->green + draft/parity/mixed-room pins, 146/146) and
CrownUpdateHearingScheduleOnlyIT (schedule-only allocate + ADR-005 draft mirror,
red 90s-timeout on allocated=false -> green 2/2).

…s block total + anchor

- validate CROWN update payload shape (CrownNonDefaultDaysValidator, 400 on violation):
  at most one virtual=true nonDefaultDay; startDate must equal the virtual day's
  date; genuine (non-virtual) days must fall within startDate..endDate
- multi-day booking uses the virtual day's duration as the block TOTAL and its
  courtScheduleId/date as the anchor sent to courtscheduler, instead of summing
  every day (a mixed proxy+genuine payload double-counted, e.g. 1440+360=1800,
  and over-booked a 5th session past the requested endDate)
- after session extraction, hearingDays whose date matches a genuine nonDefaultDay
  take that day's startTime (list-response times previously always won)

…eduler, CROWN listing-side, past-only)

Adds listing.command.move-hearing-to-past-date as a new content-type action on the
existing POST /hearings/{hearingId} resource. ListingCommandApi resolves the hearing
from the listing viewstore (new HearingLookupService, mirroring the existing
command.service.HearingService query-view lookup pattern) and rejects unknown
hearingIds with 422 HEARING_ID_NOT_FOUND before anything is sent.

MAGISTRATES hearings call courtscheduler synchronously via
CourtSchedulerServiceAdapter.moveHearingToPastDate (new HearingSlotsService POST to
/hearings/{hearingId}, application/vnd.courtscheduler.move-hearing-to-past-date+json);
a 2xx response enriches the command with a purpose-built MoveHearingToPastDateResult
and the enriched handler applies it via the existing
raiseHearingDayCourtSchedulesUpdated/HearingDayCourtScheduleUpdated event. A non-2xx
response raises MoveHearingToPastDateException, rendered as 422/404 by the new
MoveHearingToPastDateExceptionMapper (registered via the new
ListingCommandCommonProviders @specializes DefaultCommonProviders) - no event is sent.

CROWN hearings never call courtscheduler (Baris decision D1): the command-api
validates past-only (422 FUTURE_DATE_NOT_ALLOWED) and the enriched handler re-dates
the hearing purely listing-side by reusing the existing Hearing.changeStartDate
aggregate method (StartDateChangedForHearing event) - no new domain event needed.

Permission: PermissionConstants.createChangeHearingToPastDatePermission() (object
"Change hearing to past date", action "Link") plus a DRL rule using
userAndGroupProvider.hasPermission(...).

Adds MoveHearingToPastDateIT plus CourtSchedulerServiceStub/WireMockStubUtils
extensions and MAGS/CROWN test-data fixtures.

…(path-only)

The courtscheduler crown.search.and.book / mags.search.and.book request schemas
were reshaped to additionalProperties:false with hearingId removed (SPRDT-1089 /
team-pasthearings SPRDT-985 contract). hearingId now travels only in the
/hearings/{hearingId} path and is injected by the courtscheduler REST adapter.

HearingSlotsService.postSearchBook still built the body from ALL params, including
hearingId, so every CROWN search-and-book (list-new-hearing, update-hearing-for-
listing, MCC, adjournment) was rejected 400 by the strict schema -> allocation
aborted (CrownFallbackInvalidRequestException) -> CrownScheduledListingIT failed.

Exclude hearingId from the search-and-book body, matching the move-hearing-to-past-
date caller which already follows the reshaped contract. Adds a regression guard.

SPRDT-1011 vs SPRDT-1089 contract skew fix.

…he selected court centre, not a court-schedule id

In enrichCrownUpdateHearing the courtCentreId query param passed to
multiDaySearchAndBook fell back to anchorCourtScheduleId when
hearing.getCourtCentreId() was null — a court-schedule UUID, not a
court-centre UUID, so courtscheduler received a bogus courtCentreId
(400 / mis-booking). Fall back to the hearing's own selected court
centre (getSelectedCourtCentre().getId()) instead, mirroring the
fallback pattern in the sibling handleCrownMultiDayEnrichment.